File\i386\biosinfo.inf could not be loaded.

**ackain** · July 24, 2010

我用WinSetup-1-0-beta6制作了一个USB的windows xp安装盘。

我安装windows xp时，出现以下信息：

The error code is 2

Setup cannot continue.Press any key to exit.

不知道什么回事！

**jaclaz** · July 24, 2010

Maybe right question, but WRONG place to ask it.

This is the "generic":

MSFN Forums

> Microsoft Software Products - Discussion & Support

> Windows XP

section

There is a specific section here about "Install Windows from USB":

http://www.msfn.org/board/forum/157-install-windows-from-usb/

BEFORE anything else do use the Search function of the Forum use "\i386\biosinfo.inf " in the "Find words" and select "install Windows form USB" in "Find in Forum".

Read the resulting topics.

There may be several reasons for that error, most notably an uncorrect use of the app or a "strange" source.

Hopefully a Moderator will move this thread there.

jaclaz

**Tripredacus** · July 25, 2010

I can move it. In addition:

2.d Be mindful of other users on this forum and post in English. If you must post in your native tongue, please include an English translation so that it can be better read and responded to by the rest of the forum members; if it ends up being a useful post, others will be able to view and read it later. This site is unilingual, so be mindful of that when you post.

**beserk1** · August 8, 2010

我用WinSetup-1-0-beta6制作了一个USB的windows xp安装盘。
我安装windows xp时，出现以下信息：
File\i386\biosinfo.inf could not be loaded.
The error code is 2
Setup cannot continue.Press any key to exit.
不知道什么回事！

I used WinSetup-1-0-beta6 and made a windows xp installation USB
When I install windows xp, the following error was shown:
File\i386\biosinfo.inf could not be loaded.
The error code is 2
Setup cannot continue.Press any key to exit.
Dont know why!

above is the translation

I am having the same problem, I went to search and only got 3 threads, the closest one I think is this one

Funny thing is that the usb I made work on all the machines but one, that gave me the above error.

Anyone can help us out?

**jaclaz** · August 8, 2010

I am having the same problem, I went to search and only got 3 threads, the closest one I think is this one

Where the original problem was actually solved.

Funny thing is that the usb I made work on all the machines but one, that gave me the above error.

Hmmm , compare with this :

http://www.msfn.org/board/index.php?showtopic=140479&st=56

You seem to fail to attribute the right "focus" of the problem: it has NOTHING to do with the actual sticks, it is all about the way a given motherboard BIOS behaves.
In other words the SAME stick "normally" partitioned/formatted with, say, the HP utility may boot allright on 99 motherboards and fail on the 100th.

Anyone can help us out?

YES.

http://homepages.tesco.net/J.deBoynePollard/FGA/questions-with-yes-or-no-answers.html

Can you try the suggestion already given on that thread?

Or have you already tried them all and nothing came out of it?

In any case you need to provide some more details.

jaclaz

**beserk1** · August 8, 2010

Can you try the suggestion already given on that thread?
Or have you already tried them all and nothing came out of it?
In any case you need to provide some more details.

I notice the files I have and the ones from that thread is not the same, I could only assume thats because after the issue was solved on the thread, the developer updated the files. Thus I couldn't try all of them.

But the ones I tried still give me the error.

Tell me what details you need and I will get them up.

Here are some result from grub command line

find /winsetup.lst

(hd0,0)

root (

+ TAB

Possible disks are: fd0 hd0 hd1 rd

where as if I do it on one of the machine that works

Possible disks are: hd0 hd1 rd

**beserk1** · August 8, 2010

here are some more result from command line

root

(hd0,0):Filesystem type is ntfs, partition type 0x07

do you want me to do THIS? If so, where should I put that piece of code in menu.lst?

I also want to try what was mentioned HERE, but I couldn't locate BootDevice= in my txtsetup.sif

Edited August 8, 2010 by beserk1

**jaclaz** · August 8, 2010

Let's start with some order.

Remove any menu.lst from your USB stick (this way you get to command line automatically).

Make a copy of it somewhere AND post here it's contents.

If you simply run

root

[ENTER]

and you get (hd0,0) as reply , it means that the USB stick (boot device, and automatically root when booted in grub4dos) is seen correctly as first hard disk. (so you are NOT in the situation where the USB stick is detected as floppy)

now, type:

find /

[TAB]

you should have a list of the files/directories you find in the root of the stick, please post these filenames/directory names listed.

Now some details.

What are your Sources? (like XP English/Chinese/Whatever, SP1, SP2 SP3, etc.)

Which exact version of the WinsetupfromUSB are you testing with? There are TWO valid versions to try, 0.2.3 (traditional) and 1.0 beta6 (new method).

How big is the stick?

Which app did you use to partition/format it?

Also connected to the above question type in grub4dos:

geometry (hd0)

{ENTER]

and post results.

jaclaz

**beserk1** · August 8, 2010

Remove any menu.lst from your USB stick (this way you get to command line automatically).
Make a copy of it somewhere AND post here it's contents.

uploaded it here

find /
[TAB]
you should have a list of the files/directories you find in the root of the stick, please post these filenames/directory names listed.

BOOTWS/

nLite/

WINSETUP/

plpbt.bin

default

grldr

windefault

winsetup.lst

usbdrive.tag

Now some details.
What are your Sources? (like XP English/Chinese/Whatever, SP1, SP2 SP3, etc.)

XP english sp3, customized with nlite, no input needed

Which exact version of the WinsetupfromUSB are you testing with? There are TWO valid versions to try, 0.2.3 (traditional) and 1.0 beta6 (new method).

1.0 beta 6

How big is the stick?

16gb

Which app did you use to partition/format it?

did everything from format to copying the file in WinSetupFromUSB 1.0 beta 6

Also connected to the above question type in grub4dos:
geometry (hd0)
{ENTER]
and post results.

drive 0x80(LBA): C/h/S=1024/255/63, Sector Count/Size=31342815/512

Partition num: 0, active, Filesystem type is ntfs, partition type 0x07

**jaclaz** · August 8, 2010

Good, everything seems "cool", you have the usbdrive.tag allright, then the only part that is interesting is this:

title Windows XP/2000/2003 Setup
map --unmap=0:0xff
map --unhook
savedefault
find --set-root --ignore-cd /usbdrive.tag
configfile /winsetup.lst

So you need to post also contents of winsetup.lst .

jaclaz

**beserk1** · August 8, 2010

So you need to post also contents of winsetup.lst .

haha, working late here, slipped


color black/cyan yellow/cyan
timeout 10
default /windefault

title Back to Main Menu
configfile /menu.lst


title First part of Windows XP Professional SP3 setup from partition 0
map --unmap=0:0xff
map --unhook
map --mem (hd0,0)/WINSETUP/XPpSP3.ISO (0xff)
savedefault 2
checkrange 0x00,0x01 read 0x8280 && configfile /BOOTWS/fd.lst
geometry (hd9) && configfile /BOOTWS/10.lst
geometry (hd8) && configfile /BOOTWS/9.lst
geometry (hd7) && configfile /BOOTWS/8.lst
geometry (hd6) && configfile /BOOTWS/7.lst
geometry (hd5) && configfile /BOOTWS/6.lst
geometry (hd4) && configfile /BOOTWS/5.lst
geometry (hd3) && configfile /BOOTWS/4.lst
geometry (hd2) && configfile /BOOTWS/3.lst
geometry (hd1) && configfile /BOOTWS/2.lst
geometry (hd0) && configfile /BOOTWS/1.lst
boot
map --unmap=0:0xff
map --unhook

title Second part of 2000/XP/2003 setup / Boot first internal hard disk
geometry (hd9) && configfile /BOOTWS/10.lst
geometry (hd8) && configfile /BOOTWS/9.lst
geometry (hd7) && configfile /BOOTWS/8.lst
geometry (hd6) && configfile /BOOTWS/7.lst
geometry (hd5) && configfile /BOOTWS/6.lst
geometry (hd4) && configfile /BOOTWS/5.lst
geometry (hd3) && configfile /BOOTWS/4.lst
geometry (hd2) && configfile /BOOTWS/3.lst
geometry (hd1) && configfile /BOOTWS/2.lst
geometry (hd0) && configfile /BOOTWS/1.lst
boot

**ilko_t** · August 8, 2010

Comment out this line in winsetup.lst (put # at front) or just delete it:

checkrange 0x00,0x01 read 0x8280 && configfile /BOOTWS/fd.lst

and try again.

Can you also post result of:

geometry (fd0)

**jaclaz** · August 8, 2010

Good ,

now, depending on the amount of hard disks you have connected to that PC, you have to find out which among the 10.lst, 9.lst ... 1.lst is actually used (most probably it's 2.lst) and post it's contents.

(what I am trying to find out is the sequence of grub4dos commands that are actually issued on that machine, and recreate a single menu.lst entry with them, that we can later experiment with/modify)

jaclaz

**cdob** · August 8, 2010

I also want to try what was mentioned HERE, but I couldn't locate BootDevice= in my txtsetup.sif

map --mem (hd0,0)/WINSETUP/XPpSP3.ISO (0xff)

txtsetup.sif is used from inside /WINSETUP/XPpSP3.ISO

**beserk1** · August 9, 2010

Comment out this line in winsetup.lst (put # at front) or just delete it:
checkrange 0x00,0x01 read 0x8280 && configfile /BOOTWS/fd.lst
and try again.

no difference, still get the error code 2 with biosinfo.inf

Can you also post result of:
geometry (fd0)

drive 0x00(CHS): C/H/S=80/2/18,Sector Count/Size=2880/512

now, depending on the amount of hard disks you have connected to that PC, you have to find out which among the 10.lst, 9.lst ... 1.lst is actually used (most probably it's 2.lst) ....

not sure on how to do that, but going to delet the .lst from 10 to 1 and check when it stop working

will report back later

fd.lst


checkrange 0x01 read 0x8280 && map (fd1) (fd0)
map --hook
ls (0xff)/ && root (0xff)
ls (0xff)/ && chainloader /I386/SETUPLDR.BIN
ls (0xff)/I386/ && cat --locate=rdisk(1)partition(1) --replace=fdisk(0)partition(0) (0xff)/I386/TXTSETUP.SIF
ls (0xff)/AMD64/ && cat --locate=rdisk(1)partition(1) --replace=fdisk(0)partition(0) (0xff)/AMD64/TXTSETUP.SIF
boot

10.lst


map (hd0) (hd9)
map (hd1) (hd0)
map (hd2) (hd1)
map (hd3) (hd2)
map (hd4) (hd3)
map (hd5) (hd4)
map (hd6) (hd5)
map (hd7) (hd6)
map (hd8) (hd7)
map (hd9) (hd8)
map --hook
ls (0xff)/ && root (0xff)
ls (0xff)/I386/ && cat --locate=rdisk(1) --replace=rdisk(9) (0xff)/I386/TXTSETUP.SIF
ls (0xff)/AMD64/ && cat --locate=rdisk(1) --replace=rdisk(9) (0xff)/AMD64/TXTSETUP.SIF
ls (0xff)/ && chainloader /I386/SETUPLDR.BIN
ls (0xff)/ || rootnoverify (hd0)
ls (0xff)/ || chainloader (hd0)+1
boot

9.lst


map (hd0) (hd8)
map (hd1) (hd0)
map (hd2) (hd1)
map (hd3) (hd2)
map (hd4) (hd3)
map (hd5) (hd4)
map (hd6) (hd5)
map (hd7) (hd6)
map (hd8) (hd7)
map --hook
ls (0xff)/ && root (0xff)
ls (0xff)/I386/ && cat --locate=rdisk(1) --replace=rdisk(8) (0xff)/I386/TXTSETUP.SIF
ls (0xff)/AMD64/ && cat --locate=rdisk(1) --replace=rdisk(8) (0xff)/AMD64/TXTSETUP.SIF
ls (0xff)/ && chainloader /I386/SETUPLDR.BIN
ls (0xff)/ || rootnoverify (hd0)
ls (0xff)/ || chainloader (hd0)+1
boot

8.lst


map (hd0) (hd7)
map (hd1) (hd0)
map (hd2) (hd1)
map (hd3) (hd2)
map (hd4) (hd3)
map (hd5) (hd4)
map (hd6) (hd5)
map (hd7) (hd6)
map --hook
ls (0xff)/ && root (0xff)
ls (0xff)/I386/ && cat --locate=rdisk(1) --replace=rdisk(7) (0xff)/I386/TXTSETUP.SIF
ls (0xff)/AMD64/ && cat --locate=rdisk(1) --replace=rdisk(7) (0xff)/AMD64/TXTSETUP.SIF
ls (0xff)/ && chainloader /I386/SETUPLDR.BIN
ls (0xff)/ || rootnoverify (hd0)
ls (0xff)/ || chainloader (hd0)+1
boot

7.lst


map (hd0) (hd6)
map (hd1) (hd0)
map (hd2) (hd1)
map (hd3) (hd2)
map (hd4) (hd3)
map (hd5) (hd4)
map (hd6) (hd5)
map --hook
ls (0xff)/ && root (0xff)
ls (0xff)/I386/ && cat --locate=rdisk(1) --replace=rdisk(6) (0xff)/I386/TXTSETUP.SIF
ls (0xff)/AMD64/ && cat --locate=rdisk(1) --replace=rdisk(6) (0xff)/AMD64/TXTSETUP.SIF
ls (0xff)/ && chainloader /I386/SETUPLDR.BIN
ls (0xff)/ || rootnoverify (hd0)
ls (0xff)/ || chainloader (hd0)+1
boot

6.lst


map (hd0) (hd5)
map (hd1) (hd0)
map (hd2) (hd1)
map (hd3) (hd2)
map (hd4) (hd3)
map (hd5) (hd4)
map --hook
ls (0xff)/ && root (0xff)
ls (0xff)/I386/ && cat --locate=rdisk(1) --replace=rdisk(5) (0xff)/I386/TXTSETUP.SIF
ls (0xff)/AMD64/ && cat --locate=rdisk(1) --replace=rdisk(5) (0xff)/AMD64/TXTSETUP.SIF
ls (0xff)/ && chainloader /I386/SETUPLDR.BIN
ls (0xff)/ || rootnoverify (hd0)
ls (0xff)/ || chainloader (hd0)+1
boot

5.lst


map (hd0) (hd4)
map (hd1) (hd0)
map (hd2) (hd1)
map (hd3) (hd2)
map (hd4) (hd3)
map --hook
ls (0xff)/ && root (0xff)
ls (0xff)/I386/ && cat --locate=rdisk(1) --replace=rdisk(4) (0xff)/I386/TXTSETUP.SIF
ls (0xff)/AMD64/ && cat --locate=rdisk(1) --replace=rdisk(4) (0xff)/AMD64/TXTSETUP.SIF
ls (0xff)/ && chainloader /I386/SETUPLDR.BIN
ls (0xff)/ || rootnoverify (hd0)
ls (0xff)/ || chainloader (hd0)+1
boot

4.lst


map (hd0) (hd3)
map (hd1) (hd0)
map (hd2) (hd1)
map (hd3) (hd2)
map --hook
ls (0xff)/ && root (0xff)
ls (0xff)/I386/ && cat --locate=rdisk(1) --replace=rdisk(3) (0xff)/I386/TXTSETUP.SIF
ls (0xff)/AMD64/ && cat --locate=rdisk(1) --replace=rdisk(3) (0xff)/AMD64/TXTSETUP.SIF
ls (0xff)/ && chainloader /I386/SETUPLDR.BIN
ls (0xff)/ || rootnoverify (hd0)
ls (0xff)/ || chainloader (hd0)+1
boot

3.lst


map (hd0) (hd2)
map (hd1) (hd0)
map (hd2) (hd1)
map --hook
ls (0xff)/ && root (0xff)
ls (0xff)/I386/ && cat --locate=rdisk(1) --replace=rdisk(2) (0xff)/I386/TXTSETUP.SIF
ls (0xff)/AMD64/ && cat --locate=rdisk(1) --replace=rdisk(2) (0xff)/AMD64/TXTSETUP.SIF
ls (0xff)/ && chainloader /I386/SETUPLDR.BIN
ls (0xff)/ || rootnoverify (hd0)
ls (0xff)/ || chainloader (hd0)+1
boot

2.lst


map (hd0) (hd1)
map (hd1) (hd0)
map --hook
ls (0xff)/ && root (0xff)
ls (0xff)/ && chainloader /I386/SETUPLDR.BIN
ls (0xff)/ || rootnoverify (hd0)
ls (0xff)/ || chainloader (hd0)+1
boot

1.lst


map --hook
ls (0xff)/ && root (0xff)
ls (0xff)/I386/ && cat --locate=rdisk(1) --replace=rdisk(0) (0xff)/I386/TXTSETUP.SIF
ls (0xff)/AMD64/ && cat --locate=rdisk(1) --replace=rdisk(0) (0xff)/AMD64/TXTSETUP.SIF
ls (0xff)/ && chainloader /I386/SETUPLDR.BIN
ls (0xff)/ || rootnoverify (hd0)
ls (0xff)/ || chainloader (hd0)+1
boot

I also want to try what was mentioned HERE, but I couldn't locate BootDevice= in my txtsetup.sif
map --mem (hd0,0)/WINSETUP/XPpSP3.ISO (0xff)
txtsetup.sif is used from inside /WINSETUP/XPpSP3.ISO

I could modify the iso, is that what needs to be done?

Edited August 9, 2010 by beserk1

Sign In

File\i386\biosinfo.inf could not be loaded.

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Create an account or sign in to comment

Create an account

Sign in

Recently Browsing 0 members