Cannot install Win XP MCE OEM or Win XP Pro
cact25
ran for 25+ hrs and found no errors in 4 GB Mem. Ubuntu installed but Win
install gets a stop 0x0000007B.
Jim
Shenan Stanley
Didn't look up the error, eh?
Find out what controller (hard drive) needs to be loaded using the F6 method
and a floppy disk drive and/or integrated into the Windows XP installation
media of your choice using various methods. For most a cheap USB floppy
diskette drive and a floppy and a download of the HDD controller driver is
easier/faster than integrating the driver into the Windows XP installation
media.
Google "F6 during Windows XP install"...
Then Google for the motherboard you have in said system and/or go to the
manufacturer's web page (if a third tier computer like Dell, HP, IBM, etc)
and find the controller driver (if available for Windows XP even) and use it
during the install accordingly.
--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html
cact25
you can find the answer, i would really appreciate it. I could not find it.
It never gets to the point where you have the option of F6. BartPE does the
same thing. I have been in constant contact with the tech people at Gigabyte
(the mobo mfr.) They said that their are no SATA drivers required. The didk
that comes with the mobo is used after their is an OS installed. The BIOS is
set to handle SATA in legacy or native mode. Neither works - same STOP
either way. The PC does not have a floppy. It is strange that Linux does
not have a problem with it.
Shenan Stanley
> I cannot install Win XP MCE OEM or Win XP Pro on a new built PC.
> Memtest86+ ran for 25+ hrs and found no errors in 4 GB Mem. Ubuntu
> installed but Win install gets a stop 0x0000007B.
Shenan Stanley wrote:
> Didn't look up the error, eh?
>
> Find out what controller (hard drive) needs to be loaded using the
> F6 method and a floppy disk drive and/or integrated into the
> Windows XP installation media of your choice using various methods.
> For most a cheap USB floppy diskette drive and a floppy and a
> download of the HDD controller driver is easier/faster than
> integrating the driver into the Windows XP installation media.
>
> Google "F6 during Windows XP install"...
>
> Then Google for the motherboard you have in said system and/or go
> to the manufacturer's web page (if a third tier computer like Dell,
> HP, IBM, etc) and find the controller driver (if available for
> Windows XP even) and use it during the install accordingly.
cact25 wrote:
> As a matter of fact, I did look it up and found meaningless
> information. If you can find the answer, i would really appreciate
> it. I could not find it. It never gets to the point where you have
> the option of F6. BartPE does the same thing. I have been in
> constant contact with the tech people at Gigabyte (the mobo mfr.)
> They said that their are no SATA drivers required. The didk that
> comes with the mobo is used after their is an OS installed. The
> BIOS is set to handle SATA in legacy or native mode. Neither works
> - same STOP either way. The PC does not have a floppy. It is
> strange that Linux does not have a problem with it.
Please give the exact make/model of the motherboard. I'd like to look at
their driver page.
I believe you need to install the HDD Controller (mass storage drivers)
during the installation of Windows XP (whatever flavor) using actually
media - not recovery disks, etc. In order to do this, you need the HDD
controller (mass storage) drivers and a floppy diskette (and drive.) You
can also get the correct mass storage (HDD controller) drivers and integrate
them into your installation media, although this is more time consuming for
most.
It is *not* strange that *nix handles it - as it may have the drivers
integrated in and/or have no need of that type of access.
I never said you had a floppy - I said in order to use the F6 method of
install - you will need a floppy diskette (and drive) and for most it is
easy to just get a USB cheapo for this.
If the motherboard does not have drivers that can be used during the install
of Windows XP and your installation media is good (I'd also encourage SP2
installation media or beyond) and this is not working for you - there are
two possibilities.
1) They (the motherboard manufacturer) don't support Windows XP for that
motherboard.
2) The motherboard (some component of it) is defective.
BartPE has the same problem if you do not have the needed Mass Storage
drivers integrated (using something like http://driverpacks.net/).
If your install is never getting to the point of choosing F6 (very early in
the install process) - then you have some serious issues (Is the
installation media modified in any way? Automated?) How early in the
process?
http://www.michaelstevenstech.com/cleanxpinstall.html#steps
Step 5 - really soon after you press any key to boot from CD.
( http://pcsupport.about.com/od/operatingsystems/ss/instxpclean1.htm -->
Third page, next twice.)
As for looking up there error - I would suggest something along the lines
of:
what is 0x0000007B during "Windows XP" installation
http://www.google.com/search?q=what+is+0x0000007B+during+%22Windows+XP%22+installation
Which might get you to:
Advanced troubleshooting for "Stop 0x0000007B" errors in Windows XP
http://support.microsoft.com/kb/324103
And/or
http://www.computing.net/answers/windows-xp/stop-0x0000007b-during-winxp-install/27252.html
Now - admittedly - I am giving you the most common issue/resolution for this
problem.
- You could have a jumper set incorrectly on your hard disk drive (check all
the hard disk drive manuals for this information.) I find this unlikely.
- You could have a bad hard disk drive (download/utilize the hard disk drive
manufacturer's diagnostics to determine this.) I find this plausible - but
only a check will prove either way. ( Yeah yeah - I know - linux installs.
I am sure Windows 98SE would too - not everything is as picky as Windows XP.
;-) )
- You might benefit from using the hard drive manufacturer's utility to
zero-write the drive - getting rid of all old information on it so you
actually start with a clean slate (MBR).
That's where you are at. Let us know where you go.
cact25
http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ProductID=3013
and the memory is Corsair CM2x1024-6400
http://www.corsair.com/_datasheets/CM2X1024-6400.pdf
The case is a Raidmax Smilodon 500W
http://www.raidmax.com/httpdocs/main.htm
The CPU is an Intel E8400 Core 2 Duo.
HTH
Jim
Anna
"cact25" <cac...@discussions.microsoft.com> wrote in message
news:C9977BD7-DFB2-489B...@microsoft.com...
> The mobo is a Gigabyte EP45-UD3R.
> http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ProductID=3013
> and the memory is Corsair CM2x1024-6400
> http://www.corsair.com/_datasheets/CM2X1024-6400.pdf
> The case is a Raidmax Smilodon 500W
> http://www.raidmax.com/httpdocs/main.htm
> The CPU is an Intel E8400 Core 2 Duo.
>
> HTH
>
> Jim
Jim:
First off, let me quickly state that I'm not at all familiar with Linux so
my comments that follow would *not* take into consideration any
problem/issue that Linux might be causing re this situation. I just want to
make that clear at the outset.
I'm quite familiar with that Gigabyte board having installed it in quite a
few machines in an XP environment. As you've inferred and as Gigabyte tech
support (at least that's what they call themselves! But that's another
story) has stated, auxiliary SATA controller drivers are unnecessary for
SATA HDD recognition in a non-RAID configuration.
The BIOS default settings as they apply to the SATA device should suffice
for XP OS detection of the disk. So in the "Integrated Peripherals" section
of the BIOS settings, check that the first three SATA settings in that
section are Disabled, the "Onboard SATA/IDE Device" set to Enabled, and the
"Onboard SATA/IDE Ctrl Mode" is set to IDE.
Anna
Shenan Stanley
cact25 wrote:
> The mobo is a Gigabyte EP45-UD3R.
>
> http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ProductID=3013
> and the memory is Corsair CM2x1024-6400
> http://www.corsair.com/_datasheets/CM2X1024-6400.pdf
> The case is a Raidmax Smilodon 500W
> http://www.raidmax.com/httpdocs/main.htm
> The CPU is an Intel E8400 Core 2 Duo.
>
> HTH
Not me you are trying to help - it's you. ;-) Thanks for the sentiment
though.
I see Anna replied with some BIOS settings. Don't know if you are using any
RAID or not - but... It wouldn't hurt to use the drivers your motherboard
has supplied on the web page for the F6 method of installation...
http://www.gigabyte.com.tw/Support/Motherboard/Driver_Model.aspx?ProductID=2921&ost=xp#anchor_os
(SATA RAID --> Intel ICH9R/ICH10R Driver (Preinstall driver) "Note: Press F6
during Windows* setup to read from floppy. (For non-VISTA operating
systems)"
As I said - won't hurt to try it - might fix everything in fact. Maybe the
zero-write would to (for the MBR - little overkill, but...)
cact25
I only downloaded it to try and see if it would install after numerous
attempts at trying to install Win. It was just a test to see if anything
would install. And, it did.
cact25
I actually had the Onboard SATA/IDE Device Disabled to force legacy IDE mode
when having it set to Enabled to force native IDE mode did not work. The
other 2 have not been changed since I don't want RAID.
Jim
cact25
use. Gigabyte and the manual that came with the mobo don't require any
drivers to be preinstalled if no RAID. I also don't have a floppy on any of
my PC's. The floppy is required if you are going to set up RAID, however.
Jim
Shenan Stanley
Shenan Stanley wrote:
> Not me you are trying to help - it's you. ;-) Thanks for the
> sentiment though.
>
> I see Anna replied with some BIOS settings. Don't know if you are
> using any RAID or not - but... It wouldn't hurt to use the drivers
> your motherboard has supplied on the web page for the F6 method of
> installation...
>
> http://www.gigabyte.com.tw/Support/Motherboard/Driver_Model.aspx?ProductID=2921&ost=xp#anchor_os
> (SATA RAID --> Intel ICH9R/ICH10R Driver (Preinstall driver) "Note:
> Press F6 during Windows* setup to read from floppy. (For non-VISTA
> operating systems)"
>
> As I said - won't hurt to try it - might fix everything in fact.
> Maybe the zero-write would to (for the MBR - little overkill,
> but...)
cact25 wrote:
> I'm not using RAID, and the settings Anna gave me are what I have
> tried to use. Gigabyte and the manual that came with the mobo
> don't require any drivers to be preinstalled if no RAID. I also
> don't have a floppy on any of my PC's. The floppy is required if
> you are going to set up RAID, however.
I still say you should try using the drivers (F6 and/or integration) and
possibly do the zero-write on the hard disk drive using the manufacturer's
utility (although the latter is less likely the issue.)
Borrowing/purchasing a cheap USB floppy disk drive or trying to integrate
the drivers into your installation media (not hard at all using something
like nLite or driverpacks...) will most likely fix the issue you are having.
If you want to test it in an easier way first...
Download the UBCD4Win creation utility, create a UBCD4Win (which is a BartPE
CD on crack) CD and make sure you include (using the Plugins) the
driverpacks for Mass Storage - updating the driverpacks before you create
the ISO/burn the CD. If the UBCD4Win boots - you've proven what it is you
need in order to fix your problem. If it doesn't boot - you've proven
something is likely wrong with the hardware somewhere down the line.
Come back - let us know.
http://www.walmart.com/catalog/product.do?product_id=5712847
http://www.bestbuy.com/site/olspage.jsp?skuId=6307436&type=product&id=1074787976171
http://www.nliteos.com/
http://driverpacks.net/
*shrug* It's your time.
Anna
> "Anna" wrote:
>> Jim:
>> First off, let me quickly state that I'm not at all familiar with Linux
>> so
>> my comments that follow would *not* take into consideration any
>> problem/issue that Linux might be causing re this situation. I just want
>> to
>> make that clear at the outset.
>>
>> I'm quite familiar with that Gigabyte board having installed it in quite
>> a
>> few machines in an XP environment. As you've inferred and as Gigabyte
>> tech
>> support (at least that's what they call themselves! But that's another
>> story) has stated, auxiliary SATA controller drivers are unnecessary for
>> SATA HDD recognition in a non-RAID configuration.
>>
>> The BIOS default settings as they apply to the SATA device should suffice
>> for XP OS detection of the disk. So in the "Integrated Peripherals"
>> section
>> of the BIOS settings, check that the first three SATA settings in that
>> section are Disabled, the "Onboard SATA/IDE Device" set to Enabled, and
>> the
>> "Onboard SATA/IDE Ctrl Mode" is set to IDE.
>> Anna
"cact25" <cac...@discussions.microsoft.com> wrote in message
news:D8C57C45-F821-4762...@microsoft.com...
> Anna,
>
> I actually had the Onboard SATA/IDE Device Disabled to force legacy IDE
> mode
> when having it set to Enabled to force native IDE mode did not work. The
> other 2 have not been changed since I don't want RAID.
>
> Jim
Jim:
I really don't know what could be causing the non-recognition problem you
describe. I've installed that MB in at least six machines during the recent
past using the default BIOS settings re SATA disks and have never run into a
non-recognition problem that needed to be resolved by installing an
auxiliary SATA controller driver. Again, all these systems I worked with
were non-RAID configurations.
Is there any possibility you can give this another "go", but this time with
a different SATA HDD that does not include a Linux OS? Or if you have to
work with the same HDD, could you not uninstall the Linux OS? I wouldn't
think the Linux install is causing this non-recognition problem, but just to
make sure...
And if you haven't already done so it would be wise to check out the hard
disk with the diagnostic utility from the disk's manufacturer.
Anna
cact25
Linux was only installed after many attempts to install Win, so that cannot
be the problem. The Seagate disk requires that Win be installed. It is
non-bootable.
Jim
cact25
the new PC.
It comes up with an error that NTLDR is missing, even though it is there.
It could be that it wont boot from channel 4 master. It would be nice if
Linux could run Win
programs, like diskpart.
Jim
cact25
2. I have no idea what a zero-write is
3. I am downloading it now
4. How do I know what to update before burning?
5. Is integrating the same as streaming?
Jim
Shenan Stanley
> Linux was only installed after many attempts to install Win, so
> that cannot be the problem. The Seagate disk requires that Win be
> installed. It is non-bootable.
Only *one* version of the Seagate tools requires Windows be installed.
There are several versions.
http://www.seagate.com/www/en-us/support/downloads/seatools/
Specifically "SeaTools for DOS", where you can read more about it here:
http://www.seagate.com/support/seatools/SeaToolsDOSguide.pdf
"SeaTools for DOS has replaced SeaTools Desktop and PowerMax. SeaTools for
DOS can test Seagate or Maxtor Parallel ATA (PATA and IDE) and Serial ATA
(SATA) interface disc drives. Because the software boots to its own
operating system you can test your drive regardless of the OS installed on
it. You can even test a new or completely blank drive."
Some tutorials for it (including the creation of the CD or floppy diskette
version) can be found here:
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=201271
I'll suggest again you get the drivers and either try the F6 installation
and/or integration (some people call it slipstreaming) of said drivers (at
least testing it in something like BartPE/UBCD4WIN.)
The driver can be found here:
http://www.gigabyte.com.tw/Support/Motherboard/Driver_Model.aspx?ProductID=2921&ost=xp#anchor_os
(SATA RAID --> Intel ICH9R/ICH10R Driver (Preinstall driver) "Note: Press F6
during Windows* setup to read from floppy. (For non-VISTA operating
systems)"
UBCD4WIN creation application/help:
http://ubcd4win.com/
I also suggest that you get the drive diagnostic tools (we now know - or can
assume - it is a seagate drive), full test and a "Full Erase" on the drive -
just to be thorough, before your next install attempt.
"SeaTools for DOS"
http://www.seagate.com/www/en-us/support/downloads/seatools/
Shenan Stanley
Shenan Stanley wrote:
> I still say you should try using the drivers (F6 and/or
> integration) and possibly do the zero-write on the hard disk drive
> using the manufacturer's utility (although the latter is less
> likely the issue.)
>
> Borrowing/purchasing a cheap USB floppy disk drive or trying to
> integrate the drivers into your installation media (not hard at all
> using something like nLite or driverpacks...) will most likely fix
> the issue you are having.
>
> If you want to test it in an easier way first...
>
> Download the UBCD4Win creation utility, create a UBCD4Win (which is
> a BartPE CD on crack) CD and make sure you include (using the
> Plugins) the driverpacks for Mass Storage - updating the
> driverpacks before you create the ISO/burn the CD. If the UBCD4Win
> boots - you've proven what it is you need in order to fix your
> problem. If it doesn't boot - you've proven something is likely
> wrong with the hardware somewhere down the line.
>
> Come back - let us know.
>
> http://www.walmart.com/catalog/product.do?product_id=5712847
> http://www.bestbuy.com/site/olspage.jsp?skuId=6307436&type=product&id=1074787976171
>
> http://www.nliteos.com/
> http://driverpacks.net/
>
> http://ubcd4win.com/
>
> *shrug* It's your time.
cact25 wrote:
> 1. The drivers are for RAID, and I don't get to the point where I
> can press F6
> 2. I have no idea what a zero-write is
> 3. I am downloading it now
> 4. How do I know what to update before burning?
> 5. Is integrating the same as streaming?
1) Doesn't matter - use them anyway. Given all things you have described,
it really sounds like this is the right direction. Could be wrong - but you
don't lose much more than time trying and may end up with the result you
want.
As for your ability to hit F6 during the install - this leads me to believe
you *do not* have actual installation media for any version of Windows XP
you have mentioned. You have restoration CDs or something - which could be
your true show-stopper - since you *really* need an actual Windows XP
installation CD - not some heavily modified/automated version and/or recover
set that just applies an image.
2) It's a full erase of the hard drive - literally writing a "0" to every
bit on the drive - over-writing anything and everything.
3) Downloading what now? UBCD4WIN?
4) If you mean UBCD4WIN - you are mainly concerned with clicking on the
plugins, finding and selecting the DriverPacks section and making sure it is
updated. It is fairly self-explanatory - but you can get some basic
instructions for making the CD from the web page:
http://www.ubcd4win.com/howto.htm
5) 'slipstreaming' is a misnomer when it comes to Windows XP and such CDs -
IMHO. But yes - it is in this case - referrring to what I am suggesting you
do.
See my other response to you in this conversation about the seagate tools
and such.
cact25
As I said before, It dies before you can hit F6. The disks are either MCE
OEM that came with the mobo/cpu pkg, or my Win XP Pro straight from MS. They
are legit install disks not restoration or recovery disks, and I have used
both sets on this PC. BartPE was built from the Win XP Pro install CD. I
downloaded UBCD4WIN and will play with it. The Seagate tools require an
operating OS to work, so Win must be installed first. I was thinking of
creating a CD using Microsoft.img to make it bootable and seeing if I could
use the win tools like diskpart without having Win installed, and then copy
the \i386 folder to the second drive and run winnt from it to begin the
install (this was advice from a MS tech person). The drives are NTFS, so DOS
won't work. Maybe I can UBUNTU to copy the files for me. I have no idea
what file system it uses.
Jim
Shenan Stanley
(but the entire conversation is indefinitely archived - link below...)
cact25 wrote:
> As I said before, It dies before you can hit F6. The disks are
> either MCE OEM that came with the mobo/cpu pkg, or my Win XP Pro
> straight from MS. They are legit install disks not restoration or
> recovery disks, and I have used both sets on this PC. BartPE was
> built from the Win XP Pro install CD. I downloaded UBCD4WIN and
> will play with it. The Seagate tools require an operating OS to
> work, so Win must be installed first. I was thinking of creating a
> CD using Microsoft.img to make it bootable and seeing if I could
> use the win tools like diskpart without having Win installed, and
> then copy the \i386 folder to the second drive and run winnt from
> it to begin the install (this was advice from a MS tech person).
> The drives are NTFS, so DOS won't work. Maybe I can UBUNTU to copy
> the files for me. I have no idea what file system it uses.
Again - please see my other post where I explain about the Seagate Tools
mistake you are making. ;-) It's actually on the very page where you
download the tools you are speaking of (for Windows) - which leads me to
think you are also just missing the F6 timing as well... It's not a long
period of time at the very beginning of the install - certainly shorter than
the static page showing you the seagate tools that I mention. ;-)
You may want to review the entire conversation carefully. If you have
unmodified Windows XP installation media - you get the F6 option and the
Seagate Tools can be used on a system with no OS on it at all. ;-)
You may want to look at response 11 (for driver and seagate tools
information) and response 4 (for more details on when you should see the F6
query from the install - it is *very* fast - easily missed.)
Otherwise - it may be time to take the system to someone more qualified.
This is not said to offend you - just that some things are more easily
figured out by someone with experience than by others. I can do a lot of
things on my car - but if I use up a certain amount of my time trying to fix
it - no matter who the help is - I have learned it is worth it to take it in
to an expert. ;-)
Daave
> <snipped>
> (but the entire conversation is indefinitely archived - link below...)
>
> cact25 wrote:
>> As I said before, It dies before you can hit F6. The disks are
>> either MCE OEM that came with the mobo/cpu pkg, or my Win XP Pro
>> straight from MS. They are legit install disks not restoration or
>> recovery disks, and I have used both sets on this PC. BartPE was
>> built from the Win XP Pro install CD. I downloaded UBCD4WIN and
>> will play with it. The Seagate tools require an operating OS to
>> work, so Win must be installed first. I was thinking of creating a
>> CD using Microsoft.img to make it bootable and seeing if I could
>> use the win tools like diskpart without having Win installed, and
>> then copy the \i386 folder to the second drive and run winnt from
>> it to begin the install (this was advice from a MS tech person).
>> The drives are NTFS, so DOS won't work. Maybe I can UBUNTU to copy
>> the files for me. I have no idea what file system it uses.
If you do it the right way, DOS can and will work.
Daave
Sorry, Shenan. that was meant for OP!
cact25
XP Pro on this pc, I saw the F6. It came much sooner than it takes for the
install to fail with the STOP on the new pc.
cact25
partition active.
Shenan Stanley
> DOS does not work with NTFS. I could not get FDISK to anything but
> make a partition active.
Natively - no.
With a third party tool - yes.
FDISK can delete NTFS partitions (NON-DOS I believe they are called.)
The UBCD4WIN I mentioned - works great for doing such things - and since it
is basically Windows XP - you can read/write to everything on the disk (NTFS
that is.)
Shenan Stanley
> I don't miss the F6. It never gets that far. When I installed
> bothe MCE and XP Pro on this pc, I saw the F6. It came much sooner
> than it takes for the install to fail with the STOP on the new pc.
If you boot with a standard, unmodified Windows XP Professional or Windows
XP Media Center Edition CD and start the installation process - you will get
an F6 prompt as long as the hardware is good/MBR is intact/accessible. If
the hardware is bad (or the other problem) - you may not get it.
Seagate Full Wipe, then try booting from the WIndows XP CD again.
Daave
> "Daave" wrote:
>>> cact25 wrote:
>>>> As I said before, It dies before you can hit F6. The disks are
>>>> either MCE OEM that came with the mobo/cpu pkg, or my Win XP Pro
>>>> straight from MS. They are legit install disks not restoration or
>>>> recovery disks, and I have used both sets on this PC. BartPE was
>>>> built from the Win XP Pro install CD. I downloaded UBCD4WIN and
>>>> will play with it. The Seagate tools require an operating OS to
>>>> work, so Win must be installed first. I was thinking of creating a
>>>> CD using Microsoft.img to make it bootable and seeing if I could
>>>> use the win tools like diskpart without having Win installed, and
>>>> then copy the \i386 folder to the second drive and run winnt from
>>>> it to begin the install (this was advice from a MS tech person).
>>>> The drives are NTFS, so DOS won't work. Maybe I can UBUNTU to copy
>>>> the files for me. I have no idea what file system it uses.
>> If you do it the right way, DOS can and will work.
> DOS does not work with NTFS. I could not get FDISK to anything but
> make a partition active.
Perhaps we're talking about different things. I was under the impression
you and Shenan were discussing Sea Tools for DOS:
http://www.seagate.com/support/seatools/SeaToolsDOSguide.pdf
But I see now you didn't respond to the specific post where he mentioned
it. All you need to do is download the .iso file and create a bootable
disk from it. Then configure your BIOS to boot off the CD and you can
check the health of the hard drive (since you're not booting off the
hard drive, it doesn't matter if it's NTFS!). And I think he suggested
you use its full erase function. Another option is DBAN:
You don't need fdisk. :-)