BIN that cannot access the drive with it's internal drivers. This is typically caused by the disk not being properly connected to the motherboard cable or disk drive jumpers or by an incorrect setting in BIOS. So, you should really re-check, re-re-check and re-re-re-check the cables and connections and the BIOS settings first thing.
As a general rule of the thumb testing something in a Virtual Machine will give you only part of the story, so, while it is an important and very convenient step in testing it can in some cases bring you to the false conclusion that something is working whuile it is not on real hardware. Another possibility is that you had a "bad burn". In VMware did you test the actual burned CD or the.
And yes, I got the same error. I had to try something since as I said that screen was flashing a little to fast for me to see the entire message. I tried using the original disk, not a copy but the original to boot from and it was a no go.
I still kept getting the same error message. The only other reason I could think they might not work is because they are more current files than the ones on the disk. A little detail I forgot from past re-install efforts. I assumed that I would have the option to install the drivers after installing the operating system but then I get this error screen with the following error message. Currently, Setup will load support for the following mass storage devices.
Is there anyone else with this motherboard or a similar MSI board that can tell which drivers I should integrate from the included driver disk into my slipstream disk??? Or can someone direct me to some drivers that would work with my particular motherboard.
I have a floppy drive, unfortunately, I can't use it since there doesn't seem to be an adapter or so I was told at Microcenter that would allow me to connect the Floppy drive to my SATA motherboard. I searched for information about how to find a work-around of installing the SATA drivers and found different posts about how to slipstream the files into the XP operating system and I did that but obviously I was doing something wrong.
I just want to be sure. In the mean time I will make a fresh disc with the only the iaStor files and will cross my fingers that this time the installation will be without issues.
One more question. Thanks again for responding to my post. So your main mode of SATA operation are:. However, in some BIOS there is another setting to further dictate SATA behaviour that includes options for "legacy" or "native" however I do not know the proper use for that setting. Well the lack of drivers in XP wasn't so much of an "issue" when it came out! It is a fairly old OS, I'd hardly expect that Windows 7 will be able to properly install without some additional driver files 10 years from now!
As far as the driver packs go, if you want to make an XP disc that is to be used on a bunch of different kinds of boards, they only one you'd really need would be the mass storage drivers.
If you want to make your XP disc install everything for you, I couldn't really say. As far as the files needed, It doesn't hurt to put the entire f6flpy-x86 folder onto the floppy disk, but having the AHCI files in there when you are using IDE may be confusing because Text Mode might list multiple drivers with the same name. As far as the EXE, the driver package I downloaded did not have one.
I see from MSI's website you didn't post if you had the first or B3 board neither of them have a floppy connector on the board. Your best bet would be to get a USB Floppy drive for systems like this. As time goes on, you'll see less and less systems that have floppy ports. I thought I mentioned what type of motherboard I had but when I checked I see that I was missing a few details.
My motherboard is P67A-C43 B3. I guess it just depends on what hardware you plan to install. All supplemental infos you can give us will help to accomplish this method. Though I am not an expert with WinPe, but maybe I can clarify some of the part related to bootpart. Thanks for your input. I will change my bootpart command replacing 1 primary partition booting Windows Server with the number of my partition where i will store my WinPE SDI image. If the partition is formated with NTFS, i should be able to extract the boot sector.
Note that if you are using the setupldr. The code to read boot. Not just txtsetup. On the fourth partition where i try to add my WinPE image built with 2K3SP1 binaries as source i have the following files:. I have to make some backup of data content and delete and recreate it to check again.
Unfortunately, when reboot done, my active partition becomes this Partition 3 and isn't bootable blinking cursor. Question: can i change the Jump value of partition 3 to EB without backing first all data is this change destructive? You need to be a member in order to leave a comment.
Sign up for a new account in our community. It's easy! Already have an account? Sign in here. Windows PE Existing user? MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Boot PE from Hard Drive. Share More sharing options Followers 0.
Prev 1 2 3 Next Page 2 of 3. Recommended Posts. By elazar , August 16, in Windows PE. I have been browsing around for the past 2 days while trying to build myself the "ultimate" bootable UFD. SIBLO is a syslinux variant which can boot load the nt kernel directly. We need to flatten the directory structure, so we are going to copy the contents of I to our folder bartpe.
It should look like this:. Here comes the fun part. We need to edit setupldr. Using Hex WorkShop or the hex editor of your choice, you are going to find all instances of 'minint', there should be 3. Build your siblo config file siblo. The siblo config file is the same as the syslinux config file. Here is mine for example:. One more thing, you can boot kernels straight from the boot prompt in siblo. DO NOT do this for bartpe. It will hang.
0コメント