ackain Posted July 24, 2010 Share Posted July 24, 2010 我用WinSetup-1-0-beta6制作了一个USB的windows xp安装盘。我安装windows xp时,出现以下信息:File\i386\biosinfo.inf could not be loaded.The error code is 2Setup cannot continue.Press any key to exit.不知道什么回事! Link to comment Share on other sites More sharing options...
jaclaz Posted July 24, 2010 Share Posted July 24, 2010 Maybe right question, but WRONG place to ask it.This is the "generic":MSFN Forums> Microsoft Software Products - Discussion & Support> Windows XPsectionThere 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 Link to comment Share on other sites More sharing options...
Tripredacus Posted July 25, 2010 Share Posted 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. Link to comment Share on other sites More sharing options...
beserk1 Posted August 8, 2010 Share Posted August 8, 2010 我用WinSetup-1-0-beta6制作了一个USB的windows xp安装盘。我安装windows xp时,出现以下信息:File\i386\biosinfo.inf could not be loaded.The error code is 2Setup cannot continue.Press any key to exit.不知道什么回事!I used WinSetup-1-0-beta6 and made a windows xp installation USBWhen I install windows xp, the following error was shown:File\i386\biosinfo.inf could not be loaded.The error code is 2Setup cannot continue.Press any key to exit.Dont know why!above is the translationI am having the same problem, I went to search and only got 3 threads, the closest one I think is this oneFunny 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? Link to comment Share on other sites More sharing options...
jaclaz Posted August 8, 2010 Share Posted 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 oneWhere 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=56You 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.htmlCan 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 Link to comment Share on other sites More sharing options...
beserk1 Posted August 8, 2010 Share Posted 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 linefind /winsetup.lst(hd0,0)root ( + TABPossible disks are: fd0 hd0 hd1 rdwhere as if I do it on one of the machine that worksPossible disks are: hd0 hd1 rd Link to comment Share on other sites More sharing options...
beserk1 Posted August 8, 2010 Share Posted August 8, 2010 (edited) here are some more result from command lineroot(hd0,0):Filesystem type is ntfs, partition type 0x07do 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 Link to comment Share on other sites More sharing options...
jaclaz Posted August 8, 2010 Share Posted 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 Link to comment Share on other sites More sharing options...
beserk1 Posted August 8, 2010 Share Posted 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 herefind /[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.bindefaultgrldrwindefaultwinsetup.lstusbdrive.tagNow some details.What are your Sources? (like XP English/Chinese/Whatever, SP1, SP2 SP3, etc.)XP english sp3, customized with nlite, no input neededWhich 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 6How big is the stick?16gbWhich app did you use to partition/format it?did everything from format to copying the file in WinSetupFromUSB 1.0 beta 6Also 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 Link to comment Share on other sites More sharing options...
jaclaz Posted August 8, 2010 Share Posted 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 Setupmap --unmap=0:0xffmap --unhooksavedefaultfind --set-root --ignore-cd /usbdrive.tagconfigfile /winsetup.lstSo you need to post also contents of winsetup.lst .jaclaz Link to comment Share on other sites More sharing options...
beserk1 Posted August 8, 2010 Share Posted August 8, 2010 So you need to post also contents of winsetup.lst .haha, working late here, slippedcolor black/cyan yellow/cyantimeout 10default /windefaulttitle Back to Main Menuconfigfile /menu.lsttitle First part of Windows XP Professional SP3 setup from partition 0map --unmap=0:0xffmap --unhookmap --mem (hd0,0)/WINSETUP/XPpSP3.ISO (0xff)savedefault 2checkrange 0x00,0x01 read 0x8280 && configfile /BOOTWS/fd.lstgeometry (hd9) && configfile /BOOTWS/10.lstgeometry (hd8) && configfile /BOOTWS/9.lstgeometry (hd7) && configfile /BOOTWS/8.lstgeometry (hd6) && configfile /BOOTWS/7.lstgeometry (hd5) && configfile /BOOTWS/6.lstgeometry (hd4) && configfile /BOOTWS/5.lstgeometry (hd3) && configfile /BOOTWS/4.lstgeometry (hd2) && configfile /BOOTWS/3.lstgeometry (hd1) && configfile /BOOTWS/2.lstgeometry (hd0) && configfile /BOOTWS/1.lstbootmap --unmap=0:0xffmap --unhooktitle Second part of 2000/XP/2003 setup / Boot first internal hard diskgeometry (hd9) && configfile /BOOTWS/10.lstgeometry (hd8) && configfile /BOOTWS/9.lstgeometry (hd7) && configfile /BOOTWS/8.lstgeometry (hd6) && configfile /BOOTWS/7.lstgeometry (hd5) && configfile /BOOTWS/6.lstgeometry (hd4) && configfile /BOOTWS/5.lstgeometry (hd3) && configfile /BOOTWS/4.lstgeometry (hd2) && configfile /BOOTWS/3.lstgeometry (hd1) && configfile /BOOTWS/2.lstgeometry (hd0) && configfile /BOOTWS/1.lstboot Link to comment Share on other sites More sharing options...
ilko_t Posted August 8, 2010 Share Posted 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.lstand try again.Can you also post result of:geometry (fd0) Link to comment Share on other sites More sharing options...
jaclaz Posted August 8, 2010 Share Posted 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 Link to comment Share on other sites More sharing options...
cdob Posted August 8, 2010 Share Posted August 8, 2010 I also want to try what was mentioned HERE, but I couldn't locate BootDevice= in my txtsetup.sifmap --mem (hd0,0)/WINSETUP/XPpSP3.ISO (0xff)txtsetup.sif is used from inside /WINSETUP/XPpSP3.ISO Link to comment Share on other sites More sharing options...
beserk1 Posted August 9, 2010 Share Posted August 9, 2010 (edited) Comment out this line in winsetup.lst (put # at front) or just delete it:checkrange 0x00,0x01 read 0x8280 && configfile /BOOTWS/fd.lstand try again.no difference, still get the error code 2 with biosinfo.infCan you also post result of:geometry (fd0)drive 0x00(CHS): C/H/S=80/2/18,Sector Count/Size=2880/512now, 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 workingwill report back laterfd.lstcheckrange 0x01 read 0x8280 && map (fd1) (fd0)map --hookls (0xff)/ && root (0xff)ls (0xff)/ && chainloader /I386/SETUPLDR.BINls (0xff)/I386/ && cat --locate=rdisk(1)partition(1) --replace=fdisk(0)partition(0) (0xff)/I386/TXTSETUP.SIFls (0xff)/AMD64/ && cat --locate=rdisk(1)partition(1) --replace=fdisk(0)partition(0) (0xff)/AMD64/TXTSETUP.SIFboot10.lstmap (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 --hookls (0xff)/ && root (0xff)ls (0xff)/I386/ && cat --locate=rdisk(1) --replace=rdisk(9) (0xff)/I386/TXTSETUP.SIFls (0xff)/AMD64/ && cat --locate=rdisk(1) --replace=rdisk(9) (0xff)/AMD64/TXTSETUP.SIFls (0xff)/ && chainloader /I386/SETUPLDR.BINls (0xff)/ || rootnoverify (hd0)ls (0xff)/ || chainloader (hd0)+1boot9.lstmap (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 --hookls (0xff)/ && root (0xff)ls (0xff)/I386/ && cat --locate=rdisk(1) --replace=rdisk(8) (0xff)/I386/TXTSETUP.SIFls (0xff)/AMD64/ && cat --locate=rdisk(1) --replace=rdisk(8) (0xff)/AMD64/TXTSETUP.SIFls (0xff)/ && chainloader /I386/SETUPLDR.BINls (0xff)/ || rootnoverify (hd0)ls (0xff)/ || chainloader (hd0)+1boot8.lstmap (hd0) (hd7)map (hd1) (hd0)map (hd2) (hd1)map (hd3) (hd2)map (hd4) (hd3)map (hd5) (hd4)map (hd6) (hd5)map (hd7) (hd6)map --hookls (0xff)/ && root (0xff)ls (0xff)/I386/ && cat --locate=rdisk(1) --replace=rdisk(7) (0xff)/I386/TXTSETUP.SIFls (0xff)/AMD64/ && cat --locate=rdisk(1) --replace=rdisk(7) (0xff)/AMD64/TXTSETUP.SIFls (0xff)/ && chainloader /I386/SETUPLDR.BINls (0xff)/ || rootnoverify (hd0)ls (0xff)/ || chainloader (hd0)+1boot7.lstmap (hd0) (hd6)map (hd1) (hd0)map (hd2) (hd1)map (hd3) (hd2)map (hd4) (hd3)map (hd5) (hd4)map (hd6) (hd5)map --hookls (0xff)/ && root (0xff)ls (0xff)/I386/ && cat --locate=rdisk(1) --replace=rdisk(6) (0xff)/I386/TXTSETUP.SIFls (0xff)/AMD64/ && cat --locate=rdisk(1) --replace=rdisk(6) (0xff)/AMD64/TXTSETUP.SIFls (0xff)/ && chainloader /I386/SETUPLDR.BINls (0xff)/ || rootnoverify (hd0)ls (0xff)/ || chainloader (hd0)+1boot6.lstmap (hd0) (hd5)map (hd1) (hd0)map (hd2) (hd1)map (hd3) (hd2)map (hd4) (hd3)map (hd5) (hd4)map --hookls (0xff)/ && root (0xff)ls (0xff)/I386/ && cat --locate=rdisk(1) --replace=rdisk(5) (0xff)/I386/TXTSETUP.SIFls (0xff)/AMD64/ && cat --locate=rdisk(1) --replace=rdisk(5) (0xff)/AMD64/TXTSETUP.SIFls (0xff)/ && chainloader /I386/SETUPLDR.BINls (0xff)/ || rootnoverify (hd0)ls (0xff)/ || chainloader (hd0)+1boot5.lstmap (hd0) (hd4)map (hd1) (hd0)map (hd2) (hd1)map (hd3) (hd2)map (hd4) (hd3)map --hookls (0xff)/ && root (0xff)ls (0xff)/I386/ && cat --locate=rdisk(1) --replace=rdisk(4) (0xff)/I386/TXTSETUP.SIFls (0xff)/AMD64/ && cat --locate=rdisk(1) --replace=rdisk(4) (0xff)/AMD64/TXTSETUP.SIFls (0xff)/ && chainloader /I386/SETUPLDR.BINls (0xff)/ || rootnoverify (hd0)ls (0xff)/ || chainloader (hd0)+1boot4.lstmap (hd0) (hd3)map (hd1) (hd0)map (hd2) (hd1)map (hd3) (hd2)map --hookls (0xff)/ && root (0xff)ls (0xff)/I386/ && cat --locate=rdisk(1) --replace=rdisk(3) (0xff)/I386/TXTSETUP.SIFls (0xff)/AMD64/ && cat --locate=rdisk(1) --replace=rdisk(3) (0xff)/AMD64/TXTSETUP.SIFls (0xff)/ && chainloader /I386/SETUPLDR.BINls (0xff)/ || rootnoverify (hd0)ls (0xff)/ || chainloader (hd0)+1boot3.lstmap (hd0) (hd2)map (hd1) (hd0)map (hd2) (hd1)map --hookls (0xff)/ && root (0xff)ls (0xff)/I386/ && cat --locate=rdisk(1) --replace=rdisk(2) (0xff)/I386/TXTSETUP.SIFls (0xff)/AMD64/ && cat --locate=rdisk(1) --replace=rdisk(2) (0xff)/AMD64/TXTSETUP.SIFls (0xff)/ && chainloader /I386/SETUPLDR.BINls (0xff)/ || rootnoverify (hd0)ls (0xff)/ || chainloader (hd0)+1boot2.lstmap (hd0) (hd1)map (hd1) (hd0)map --hookls (0xff)/ && root (0xff)ls (0xff)/ && chainloader /I386/SETUPLDR.BINls (0xff)/ || rootnoverify (hd0)ls (0xff)/ || chainloader (hd0)+1boot1.lstmap --hookls (0xff)/ && root (0xff)ls (0xff)/I386/ && cat --locate=rdisk(1) --replace=rdisk(0) (0xff)/I386/TXTSETUP.SIFls (0xff)/AMD64/ && cat --locate=rdisk(1) --replace=rdisk(0) (0xff)/AMD64/TXTSETUP.SIFls (0xff)/ && chainloader /I386/SETUPLDR.BINls (0xff)/ || rootnoverify (hd0)ls (0xff)/ || chainloader (hd0)+1bootI also want to try what was mentioned HERE, but I couldn't locate BootDevice= in my txtsetup.sifmap --mem (hd0,0)/WINSETUP/XPpSP3.ISO (0xff)txtsetup.sif is used from inside /WINSETUP/XPpSP3.ISOI could modify the iso, is that what needs to be done? Edited August 9, 2010 by beserk1 Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now