the files were updated... you are useing the old filenames
Look for yourself please---> http://3rdpartydriverpacks.thesneaky.com/wnt5_x86-32/
Only mods have access to update this thread, most of the third party packs are not done by our Mods.
You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by OverFlow
the files were updated... you are useing the old filenames
Look for yourself please---> http://3rdpartydriverpacks.thesneaky.com/wnt5_x86-32/
Only mods have access to update this thread, most of the third party packs are not done by our Mods.
but I see in \M\AM1\amdhdc.inf:
- I couldn't find that line when I read the inf,
you are correct, and it was correct before, it IS a bus extender.
Windows 2003 uses / includes a driver with the file name amdide.sys...
- so we must 'tag' our driver with the same name, and add the replace tag too... (for 2k3)
if a driver upgrades existing support then the driver must be named (Tag name) the same as the driver it is replacing...
Your code is valid for xp but probably fails at 2k3...
the corrected code above should work for 2K, XP and 2K3...
Code in my last post is now corrected ....
yeah JakeLD or Jaak... they are both masters of the mass storage pack...
mr_s or I can do it but it takes time away from graphics packs and base code when / if we do
the issue is this driver should load teh standard IDE driver from mshdc.in_ based on compatable HWID 'PCI\CC_0101'
the f6 drivers from the MB included drivers Disc did not work???... i suspect hardware issues now...
please verify connections and related hardware...
(replace cables, swap power connectors, inspect Capacitors for leakage)
reset BIOS defaults (pull battery if possable).
make sure you have the most current bios release.
Please SEARCH first / then ask over at MSFN...
XP 64 is not supported by DriverPacks
- not even for drivers... which you are not even asking about. lol
A demerit has not been awarded, since this post was properly placed in DriverPacks's "Other" sub-forum. rofl
That means I need to take a look at the txtsetup.oem file for ich10
the driver is included... In [I5] folder D\M\I5\
ichaide.inf
This controller emulates a standard IDE controller and should require no driver at all to load.
the ichaide.inf file is a dummy installer that just assigns a custom name to a standard IDE controller driver.
(please look at the inf)
Can you tell us what happens if you include no driverpacks and or no driverpacks and f6...
What mode is the controller in (AHCI ect...)?
PS if you have removed drivers with nLite or other program then your install will fail... since it uses included window drivers
JakeLD normaly does the Mass Storage pack and is the most current team member on that pack...
When i have extra time i devote it to the base code (which i am way behind on).
I normally have a winter slow down and then have more free time to deal with this stuff then.
(I am slammed right now)
I know for example that JakeLD just got back from being out of town...
I also know once the dust settles in his personal life he will pick this up.
There are only 3 or 4 active (NT 5.x) Pack Team members.
So we are spread quite thin on manpower. (As always)
Thanks for reporting - It's very important to us!
That is a cool trick... thanks cdob
~ I learned something today
excellent... well done everyone
there is another mistake not mentioned... AM1 is NOT a bus extender. ***(correction below, AM1 IS a bus extender)***
so applying what we know...
[AM]
ms_count=2
ms_1_deviceName="AMD PCI Bus Master IDE"
ms_1_tag="amdide"
ms_1_sysFile="amdbusdr.sys"
ms_1_hwids="PCI\VEN_1022&DEV_7409,PCI\VEN_1022&DEV_7411,PCI\VEN_1022&DEV_7441,PCI\VEN_1022&DEV_7469"
ms_1_isBusExtender=true
ms_1_exc_replaceifOS="w2k3"
ms_2_deviceName="AMD IDE Channel"
ms_2_tag="AmdEide"
ms_2_sysFile="AmdEide.sys"
ms_2_hwids="AMD_Primary_IDE_Channel,AMD_Secondary_IDE_Channel"
ms_2_isBusExtender=false
[AM1]
ms_count=1
ms_1_deviceName="AMD PCI SATA/IDE"
ms_1_tag="amdide1"
ms_1_sysFile="amdide.sys"
ms_1_hwids="PCI\VEN_1002&DEV_4390,PCI\VEN_1002&DEV_439C,PCI\VEN_1002&DEV_438C,PCI\VEN_1002&DEV_4376"
ms_1_isBusExtender=true
If you were really, really motivated to help us...
Could you please test this @ BartPE - Win 2K3 source?
edit...
since you have already tried threee versions of teh mass pack i suggest the info in this artical
http://support.microsoft.com/kb/330182
Try updating the BIOS.
i don't belive that the driver is the same in all three packs... but i have not looked yet...
A HWID is unique to each / any PnP devices firmware (in theory).
The OS uses the hwid reported by a device to match a driver for it (drivers 101).
it includes VENdor and DEVice info
- from your HWIDS
PCI\VEN_8086&DEV_2448&SUBSYS_00000000&REV_F3\3&B1BFB68&0&F0 : Intel(R) 82801 PCI Bridge - 2448
VENdor 8086 = Intel
DEVice 2448 = 82801 PCI Bridge
device reports PCI\VEN_8086&DEV_2448 to the OS (Win XP for example).
XP then finds that an 'Intel 82801 PCI Bridge' driver also contains that HWID too, and then uses it for that device.
- it is helpful if a driver is not found or if a wrong driver is applied or for simply identifying a particular device.
Since you have added no drivers yet... it is not (yet) relevant info
But it was nice to see that you made an effort to provide good details, I like that!
You are quite welcome.
Thanks for being a DriverPacks veteran!
Thanks Abdou... it is greatly appreciated
All good stuff in theory...
only someone with the hardware can tell us the answer for certain !
Please tell me if this works... http://downloads.driverpacks.net/DP_Mas … -32_805.7z
I believe it will
Please read this before posting another request for help http://forum.driverpacks.net/viewtopic.php?pid=4#p4
Are you installing Win 2000?, XP?, Win 2003... What service pack of that OS?
which version of DriverPacks BASE did you use?
Did you use nlite, or RVM integrator?
What is the HWID for your controller?
Where is your DPs_BASE.log? (which would have answered most of the above questions.)
If you need help, then you need to help us to help you. Details are the key! . . .
You provided almost none. the only three useful facts in your entire post could be summed up in four words
'ICH10 stop 7b 905r2'
Only two of those four words even appear in your title
you also did not indicate if you used mass 9.01 which would be nice to know...
since you are not on the testing team 905r2 is technically not supported for you...
unless someone on the team specifically asks you to test it .
I am unfamiliar with that method...
However the answer seems obvious to me... They want you to add the DriverPacks to your source.
Tutorial in my signature... please read it, and apply it to your source... test and report...
It looks as though you just did not use a DriverPacks slipstreamed source to start with...
I think if you do add DriverPacks to your source then your problems are solved!
This is as good a place to ask as any... since it is not a supported method of using DriverPacks
lol
Welcome to DriverPacks,
We will be glad to help you with anything within the scope of what we support.
(IE slipstreaming the drivers into your source)
Your fix is the correct one ... removing the HWID from txtsetup.sif
this is accomplished in the mass storage pack by removing the HWID from the list in the mass storage INI file [AM] section
[AM]
ms_count=1
ms_1_deviceName="AMD PCI Bus Master IDE"
ms_1_tag="amdide"
ms_1_sysFile="amdbusdr.sys"
ms_1_hwids="PCI\VEN_1022&DEV_7411,PCI\VEN_1022&DEV_7441,PCI\VEN_1022&DEV_7469"
ms_1_isBusExtender=true
ms_1_exc_replaceifOS="w2k3"
-
We will implement this fix in a nightly
if you get to the machine before we post the fix...
you can customize your local pack and test / report .
Thanks again for helping us to help you (and everyone else!)
PS I also think the wrong file is referenced it may be that it will also work If it is written like this.
[AM]
ms_count=1
ms_1_deviceName="AMD PCI Bus Master IDE"
ms_1_tag="amdide"
ms_1_sysFile="AmdEide.sys"
ms_1_hwids="PCI\VEN_1022&DEV_7409,PCI\VEN_1022&DEV_7411,PCI\VEN_1022&DEV_7441,PCI\VEN_1022&DEV_7469"
ms_1_isBusExtender=true
ms_1_exc_replaceifOS="w2k3"
Abdou... how did you get to 200 posts and not make it on the testing team yet?
You will find a new forum is now visible to you.
That is perfect... good details and trouble shooting...
Well done! we will address this issue soon!
Do you have a link to an OEM version of the driver?
Say... on the Asus site?
strange it isuseing a Standard Dual Channel PCI IDE Controller...
that is not a driver in the packs (it's an included windows driver you don't even need DriverPacks for that controller )
did you use nlite or somthing to remove drivers from your source?
as far as the keyboard goes you will need to check with the gurus over at UBCD4Win forum...
It is cusomary to include version numbers
IE
UBCD4Win ver?
DriverPacks BASE ver?
DriverPack MassStorage ver?
What OS and service pack did you use for your build?
you know the basics
cross posting... closed
http://forum.driverpacks.net/viewtopic. … 457#p31457
demerit has been awarded....
your CPU cooler is not functioning properly...
Overheating will cause your CPU to run at a reduced clock.
That or your MB is hosed...
AMD CPUs use an incredible amount of power.
This results in a shortened life for the CPU, MB and power supply.
Especially if you have not bought a quality MB like a Giga-Byte or DFI.
I believe if you check the Caps on the MB you may find they are ruptured.
Blown caps on the MB is a very common problem with AMD CPUs because of the insane power requirements.
CPU speed is not driver related...
although some software will adjust the settings that software is not a driver...
This is a Driver forum not a hardware forum (funny)
cross posting is frowned on, the other thread was closed...
http://forum.driverpacks.net/viewtopic.php?id=3767
I put it out to the team on the nightly server...
Looks Good to me if there are no objections we'll release it and credit you!~
DriverPacks.net Forum » Posts by OverFlow
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.142 seconds, 5 queries executed ]