• Registered: 2009-04-08
  • Posts: 7

Topic: Iastor.sys and Iastor8x.sys loaded simultaneously:

I suppose it's the same with numerous of other drivers (loaded during txtsetup and which are sharing the same name). So, I understand why there is an "overlap". But I think it can be easily avoided during DPSFNSHR's step (perhaps with a way to tag a driver as temporary and to delete registry entries during the first login ->> DeleteService). Maybe I'm wrong, if it's the case, excuse me tongue.

Here is an example:
http://images0.hiboox.com/images/1509/19a3e406f6e44f108fbb1ffb96d1cd57.png

http://images1.hiboox.com/images/1509/3717052fb08adbc21f23199854f285cd.png

http://images1.hiboox.com/images/1509/cf4878c66bb0e3d3798d5e3638dc7329.png


Drivers which may be affected:
ahcix86.sys
fastsx.sys
fasttrak.sys
fasttx2k.sys
hptmv.sys
iastor.sys
megasas.sys
nfrd960.sys
rr172x.sys
rr174x.sys
rr232x.sys
rr2340.sys
si3132.sys
symmpi.sys
ulsata.sys

Easy fix for some drivers (2k/2k3/XP):
No it doesn't work tongue

Last edited by anotherday (2009-04-12 06:21:32)

  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: Iastor.sys and Iastor8x.sys loaded simultaneously:

Sorry that fix cannot be implemented... each tag name MUST be unique

I will look at the code to see if this can be made to work (or if it will just slip through the cracks)

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • Registered: 2009-04-08
  • Posts: 7

Re: Iastor.sys and Iastor8x.sys loaded simultaneously:

I thought it was "unique" because of the os check sad

  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: Iastor.sys and Iastor8x.sys loaded simultaneously:

you may be correct...
That is only a theory
until i verify that the code actually does allow it,
without messing something up. wink

I will have to check the bartpe code and other related functions too wink

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: Iastor.sys and Iastor8x.sys loaded simultaneously:

This is really good thinking on your part smile well done!

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • Registered: 2009-04-08
  • Posts: 7

Re: Iastor.sys and Iastor8x.sys loaded simultaneously:

So if it isn't compatible with your code, there are some errors in DMP903r1 >> rr2340 for instance. And it seems that it's handled as an error case, the driver is not slipstreamed smile.

Last edited by anotherday (2009-04-12 06:46:16)

  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: Iastor.sys and Iastor8x.sys loaded simultaneously:

that would be true...

that part of the code involves thousands of lines and i don't have every one of them commited to memory wink

I belive that the tag name if duplicated will result in last driver with that name added is the only driver added (LILO). I am not positive without grabbing a BIG cup of coffee and running some tests and reading the debug output of base. or adding some flags...

But I agree with your assessment that an invalid entry would be skipped (or overwritten)

Either way i look at this like a feature request... it makes sense, Although these files do have a common name they will NOT all be copied to the same source in any supported platform. So they SHOULD be allowed to share a tagname... I just don't think it works that way now.

But I think you can look forward to this being a new feature of DriverPacks BASE, if it is not now...

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: Iastor.sys and Iastor8x.sys loaded simultaneously:

I never really did answer your original request... you distracted me with a shiny object...

Since the (mass storage) drivers are slipstreamed into the OS they become part of it the same way as all other integrated drivers that are included with windows. That means; the files, the reg entries, even dosnet and txtsetup, would need to be edited. Basicly they would need to be uninstalled. an uninstaller would need to be written or BASE could be adapted to do it if DriverPacks BASE was installed on the target machine. It is WAY to much trouble to just get rid of 10 meg of drivers that just may save your bacon if you ever upgrade your MB... wink

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • Registered: 2009-04-08
  • Posts: 7

Re: Iastor.sys and Iastor8x.sys loaded simultaneously:

Thank you overflow for the clarification smile.

  • ilko
  • Testing Team
  • Offline
  • Registered: 2007-07-08
  • Posts: 17

Re: Iastor.sys and Iastor8x.sys loaded simultaneously:

Sorry to raise the topic. Was going to ask similar question if anyone observed this behavior as I don't have a test machine to confirm my expectations.
I believe the issue is that I3 and I4 do not have iastor renamed to iastor78 and iastor86 respectively, whereas in txtsetup.sif the renamed files are used.

When during Text mode Setup detects lets say PCI\VEN_8086&DEV_3A23&CC_0106="iastor86", it will create a service with the same name, put the HWID with the service name in HKLM\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\ and copy the sys file (iastor86.sys) as this driver is critical.
This doesn't relate to GUI mode enumeration and searching for correct driver.

During GUI mode Setup will pick the inf file from \D\M\I4 and install the driver, creating another service, iastor this time, which will use iastor.sys from the same folder.
Is the above scenario correct?

I read that the reason I3 and I4 to have iastor not renamed is possible issues with driver signing:
http://forum.driverpacks.net/viewtopic. … 041#p28041

Would running 2 instances of the very same driver cause any problems, or renaming iastor in I3 and I4 is preferable?

I am creating a small batch file to allow easy change IDE->AHCI and moving around Intel boards using I1-I4 HWIDs. Renamed iastor and changed infs in I3-4 as well, but needed additional information and tests before make it public:
http://www.datafilehost.com/download-a548acb9.html