Setup doesn't detect hard drive
#1
Posted 25 January 2013 - 12:25 PM
#2
Posted 25 January 2013 - 05:07 PM
edit - does this help?
http://www.techspot....a-7-x64.127187/
This post has been edited by submix8c: 25 January 2013 - 05:09 PM
#3
Posted 26 January 2013 - 06:37 PM
submix8c, on 25 January 2013 - 05:07 PM, said:
edit - does this help?
http://www.techspot....a-7-x64.127187/
Yes, I tried that one and a driver direct from Intel. That article assumes that Window is already installed, but I'm getting stuck at the initial OS install. I'm installing Windows 7 from a flash drive, is it possible to modify boot options for setup to allow unsigned drivers?
#4
Posted 27 January 2013 - 02:42 PM
Some references -
http://social.techne...3f-eea731dba896
http://community.lan...t/message/54855
http://www.msfn.org/...s-installation/
DISM -
http://www.msfn.org/...d-driver-paths/
Last link found via Google
"windows 7" "unsigned drivers" "unattend.xml" site:msfn.orgOthers can be found that way. Appears that "Direct Injection" is the way to go.
#5
Posted 31 January 2013 - 02:12 PM
submix8c, on 27 January 2013 - 02:42 PM, said:
The window that asks where to install the operating system has a "Load Driver" option below the (empty) list of hard drives. I extracted the SATA AHCI drivers to a flash drive but since they are unsigned, it won't allow me to install them.
Attached File(s)
-
Win7_NoHDD_01.png (286.07K)
Number of downloads: 5
#6
Posted 31 January 2013 - 05:36 PM
#7
Posted 01 February 2013 - 12:07 AM
http://www.msfn.org/...017#entry913017
AutoUnattend.xml don't need to contain much sorta like this if you going to do the rest and place on root of USB
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-PnpCustomizationsWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DriverPaths>
<PathAndCredentials wcm:action="add" wcm:keyValue="1">
<Path>$WinPEDriver$</Path>
</PathAndCredentials>
</DriverPaths>
</component>
</settings>
</unattend>
just change amd64 to x86 if 32 bit
This post has been edited by maxXPsoft: 01 February 2013 - 12:10 AM
#8
Posted 03 February 2013 - 09:25 PM
#9
Posted 05 February 2013 - 02:21 AM
kahlil88, on 03 February 2013 - 09:25 PM, said:
We never know when someone posts what it could be except by trial and error. You led us to bleieve it was drivers
If you get far enough it will like the pic even linux partitions, can't say for bad partitions or whatever. Thats why I keep diskpart commands in a txt I can access.
Disk2.png (43.62K)
Number of downloads: 4
This post has been edited by maxXPsoft: 05 February 2013 - 02:30 AM
#10
Posted 05 February 2013 - 06:52 AM
kahlil88, on 25 January 2013 - 12:25 PM, said:
without further details, normally implies that the replacement hard disk was a brand new, unpartitioned and unformatted one.
The evolution of the thread seems to imply - strangely enough - that not only the "replacement" hard disk was an used/recycled one, but also an "untested" one
Additionally, the "replacement" disk evidently had some failure of some kind (of whatever extents/relevance cannot obviously say) as besides being partitioned/formatted it was left with the filesystem in a "dirty" state.
If the disk was actually replaced under warranty I would - before anything else - question the provider of the warranty, give them back the "replacement" hard disk and downright require a brand new (in a sealed box) hard disk or a refurbished AND certified one (depending on what the warranty covers, and how it covers it).
jaclaz
#11
Posted 05 February 2013 - 11:48 AM
jaclaz, on 05 February 2013 - 06:52 AM, said:
kahlil88, on 25 January 2013 - 12:25 PM, said:
without further details, normally implies that the replacement hard disk was a brand new, unpartitioned and unformatted one.
The evolution of the thread seems to imply - strangely enough - that not only the "replacement" hard disk was an used/recycled one, but also an "untested" one
Additionally, the "replacement" disk evidently had some failure of some kind (of whatever extents/relevance cannot obviously say) as besides being partitioned/formatted it was left with the filesystem in a "dirty" state.
If the disk was actually replaced under warranty I would - before anything else - question the provider of the warranty, give them back the "replacement" hard disk and downright require a brand new (in a sealed box) hard disk or a refurbished AND certified one (depending on what the warranty covers, and how it covers it).
Pretty sure I partitioned and formatted it beforehand, however this machine was having some odd power issues and I may have unplugged it on my first attempt not knowing that it wasn't recognizing the battery, thereby flagging the partition as dirty.
#12
Posted 06 February 2013 - 04:50 AM
kahlil88, on 05 February 2013 - 11:48 AM, said:
Good, then everything is explained
jaclaz



Help
Back to top









