How to use the registry to install drivers directly.
Posted 30 April 2010 - 06:31 PM
I hope it will help me to reanimate my "hostDriver" app.
Posted 30 April 2010 - 06:47 PM
Without the classes, CDDB barely does improve the number of devices that show up in device manager, over just txtsetup.sif use.
Maye i make somewhere else an error.
Posted 02 September 2013 - 09:58 AM
The microsft hotfix works when ALL the NICs going to be used to boot from iSCSI are present in computer. How to add NIC when it's different brand (the one which was not present during iSCSI installation)?
Posted 02 September 2013 - 12:02 PM
Well, knowing what causes 0x7B mostly. Assuming you
1. Install windows over Machine-Host<-Machine-x1
2. Use machine from Machine-Host<-Machine-x1
3. Test boot Machine-Host<-Machine-x2
I wonder where does Machine-x2 NIC + strorage controller information come from on this 'loop'. I mean when you boot from 'Machine-x2' the critical device does not exist, service at driver does not exist and device does not exist windows will attempt to identify at boot all these. Generally I believe this would require similar registry as I'm currently building to Mass storage controllers except you would need NIC IDs not Mass storage IDs as Mass storage stays the same, but:
* Mass Storage->NIC-HOST->NIC_2(this device is not identified correctly) [Assuming I understood correctly]
I'm just saying Windows boot progress is not same as install device detection progress which would write automatically the 'critical'-data needed to boot where ever it is installed as long the install target is exaplained to windows setup to understand it.
Edited by genetix, 02 September 2013 - 12:08 PM.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users