Jump to content

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


Recommended Posts

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) ;)

stop working after removing 10.lst to 1.lst

when I try to boot into the first part of the setup

following error

drive 0x81(LBA): C/H/S=1023/255/63, Sector Count/Size=16434495/512

geometry(hd1)

Error 15: File not found

p.s. I have only the usb drive (16gb), and an internal harddrive

Link to comment
Share on other sites


Right now what should be running is:

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

#winsetup.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

#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

So, try on command line the actual needed sequence (simplified for your setup with USB+1 internal hard disk):

map --mem (hd0,0)/WINSETUP/XPpSP3.ISO (0xff) 
map (hd0) (hd1)
map (hd1) (hd0)
map --hook
root (0xff)
chainloader /I386/SETUPLDR.BIN
boot

grub4dos will give you some feedback, at some of the lines entered, please post these output.

jaclaz

Link to comment
Share on other sites

grub4dos will give you some feedback, at some of the lines entered, please post these output.

I assume you dont want me to do anything to the menu.lst and winsetup.lst yet

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

nothing


root (0xff)

Filesystem type is iso9660, using whole disk


chainloader /I386/SETUPLDR.BIN

Will boot NTLDR from drive=0xff, partition=0xff(hidden sectors=0x0)


boot

gave me error 2

Edited by ilko_t
Quote box fixed
Link to comment
Share on other sites


boot

gave me error 2

Hmmm :unsure:.

Try with [TAB] autocompletion, i.e.

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

and then:

chainloader /

[TAB]

etc. until you complete the line, maybe there is a problem with the CaSe of the filenames? But it should not give error 2, but rather error 15... and it shouldn't print:

Will boot NTLDR from drive=0xff, partition=0xff(hidden sectors=0x0)

Seem like a problem of the .iso, but it's strange...

The only time I have seen error 2:

http://www.911cd.net/forums//index.php?showtopic=21756

it was a filesystem issue (on EXT2/3 FS, so completely unrelated)

jaclaz

Link to comment
Share on other sites

chainloader /

[TAB]

etc. until you complete the line, maybe there is a problem with the CaSe of the filenames?

Possible files are: NTDETECT.COM SETUPLDR.BIN TXTSETUP.SIF

they are in that CaSe

I dont know why it give me that error on this particular machine

I have no trouble with this same usb stick on 3 desktop and 4 laptop now

Link to comment
Share on other sites

I dont know why it give me that error on this particular machine

I have no trouble with this same usb stick on 3 desktop and 4 laptop now

Hey, wait a minute, I mistook :blushing: your

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

The error code is 2

Setup cannot continue.Press any key to exit.

for a grub4dos error 2 :(

Maybe it's some kind of RAM related error (specific to that machine) :unsure:.

If this is the case, if you use the 0.2.3 "stable" (that uses NOT the .iso mapping) it should work.

Check also (though it should NOT be related) with the modified NTDETECT.COM:

http://www.msfn.org/board/index.php?showtopic=112630

The grub4dos mapping is allright, so I don't think that re-partitioning/formatting with fbinst would do any good, but it's another semi-random attempt woth a shot.

jaclaz

Edited by jaclaz
Link to comment
Share on other sites

I dont know why it give me that error on this particular machine

Which particular machine gives the error?

May be another member solved this already.

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

I understand: this particular BIOS map a 16gb USB stick to a 1.44mb floppy drive.

Windows setup use BIOS to access boot media. This fails at such mapping: biosinfo.inf not found.

Almost all BIOS map a 16gb USB stick to a hard disk.

Windows setup does work.

Link to comment
Share on other sites

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

I understand: this particular BIOS map a 16gb USB stick to a 1.44mb floppy drive.

Windows setup use BIOS to access boot media. This fails at such mapping: biosinfo.inf not found.

Almost all BIOS map a 16gb USB stick to a hard disk.

Windows setup does work.

:w00t:

cdob having a hiccup? :unsure:

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

Can you also post result of:

geometry (fd0)

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

geometry (fd0) returns a floppy, that's normal.

geometry (hd0) returns a hard disk allright.

jaclaz

Link to comment
Share on other sites

Maybe it's some kind of RAM related error (specific to that machine) :unsure:.

If this is the case, if you use the 0.2.3 "stable" (that uses NOT the .iso mapping) it should work.

I kept getting the error

Autoit error -1

error variable must be of type object

tried reinstalling the whole wmi, no different

I am short of just taking the harddrive out and mounting it on a working machine and do up the drivers later

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...